fix: stop filing Anvil applications under "AI Agents", rename them "responsive" - #42219

Description

Two user-facing problems on the workspace applications screen.

1. ANVIL applications were filed under an "AI Agents" heading.

ApplicationsSection renders a single anvilApplications card list whose title was picked by a ternary:

title={createMessage(
  isAiAgentFlowEnabled ? AI_AGENTS_APPLICATIONS : ANVIL_APPLICATIONS,
)}

With license_ai_agent_enabled on, every ANVIL application was filed under a heading calling it an AI agent. They are not AI agents — they are ANVIL-layout applications that happen to share the list. The emptyStateMessage directly above used the same ternary. Both are removed; the heading and empty state are now unconditional.

2. The user-facing name for the ANVIL layout system becomes "responsive".

Sentence case and "applications" rather than "apps", to match every sibling rendered on the same screen — APPLICATIONS, NEW_APP, APPLICATION_CARD_LIST_ZERO_STATE. "responsive" stays lowercase mid-sentence because it is a descriptor, not a brand name.

Note FIXED_APPLICATIONS ("Classic Applications") is dead code — defined but referenced nowhere — so it is not the title-cased counterweight it appears to be. The headings that actually render are "Applications", this one, "Packages" and "Workflows".

Fixes https://linear.app/appsmith/issue/APP-15954

Scope — user-facing strings only

The internal name stays "Anvil" everywhere: the persisted appPositioning.type == ANVIL enum, LayoutSystemTypes.ANVIL, the feature flags, module paths and every data-testid. Renaming the persisted enum would require a migration and would silently un-gate every existing Anvil application, since the paid-entitlement gate keys on that literal value.

Testing

Adds ce/pages/Applications/tests/ApplicationsSection.test.tsx — two tests, both verified red against pre-fix source:

✕ titles the ANVIL application list 'Responsive applications', not 'AI Agents', …
✕ uses the responsive empty-state copy when the workspace has no ANVIL applications

TestingLibraryElementError: Unable to find an element with the text: Responsive applications.

with the printed DOM showing the heading as AI Agents and the zero state as There are no AI Agents in this workspace.

It renders ApplicationsSection deliberately, not ApplicationCardList — that component forwards title verbatim to CardList, so a test there would prove only "the component renders the title it was handed" and would pass both before and after the fix. The decision being fixed lives in ApplicationsSection.

Reverting only the ternary while leaving the string rename applied isolates the mis-filing decision from the rename.

Known issue, deliberately not fixed here

The render gate on that block is wrong, and this PR does not change it. isAnvilEnabled resolves through getIsAnvilLayoutEnabled, which reads the retired release_anvil_enabled flag — no longer in the server's FeatureFlagEnum, so never served, and defaulted to false. The gate therefore collapses to isAiAgentFlowEnabled alone.

Consequence: an organization licensed for Anvil without the AI-agent flag never renders this section at all, and because anvilApplications is partitioned out of nonAnvilApplications, its applications appear in neither list. That is pre-existing, is a behaviour change to fix, and needs its own test — so it is tracked separately rather than folded in here.

getIsAnvilLayoutEnabled's JSDoc also claims it is @deprecated DEAD / RETIRED (M5) with "ZERO production callers", which is false — ApplicationsSection is a live caller. Worth correcting alongside that fix.

Impact on existing instances

Label-only. No schema change, no migration, no persisted-data change, no flag change. Existing applications are unaffected functionally; ANVIL ones move from an "AI Agents" heading to "Responsive applications". Rollback is a revert.

Companion EE change (removing the unused AI Agent create-menu item, and renaming the EE license-gate copy and instance-setting label) ships separately in appsmith-ee and depends on this landing first, since the create-menu label lives in this file.

Automation

/ok-to-test tags="@tag.All"

Summary by CodeRabbit

• Updates
  • Updated application labels to use “Responsive” terminology, including “Responsive applications” and “Responsive application.”
  • Standardized application list headings and empty states to display responsive application messaging consistently.
  • Corrected a display issue where AI-agent labels could appear for responsive applications.